How property inspector files work

At startup, Dreamweaver reads the first line of each .htm and .html file in the Configuration/Inspectors folder, looking for the comment string that defines the type, priority, and selection type of a property inspector. Files that do not have this comment as their first line are ignored.

When the user makes a selection in Dreamweaver or moves the insertion point to a different location, the following chain of events occurs:

1	Dreamweaver looks for any inspectors that have a selection type of within.
2	If there are any within inspectors, Dreamweaver searches up the document tree from the currently selected tag to check whether there are inspectors for any of the tags that surround the selection. If—and only if—there are no within inspectors, Dreamweaver looks for any inspectors that have a selection type of exact.
3	For the first tag found that has one or more inspectors, Dreamweaver calls each inspector's canInspectSelection() function. If this function returns FALSE, Dreamweaver no longer considers the inspector a candidate for inspecting the selection.
4	If more than one potential inspector remains after calling canInspectSelection(), Dreamweaver sorts the remaining inspectors by priority.
5	If more than one potential inspector shares the same priority, Dreamweaver chooses an inspector alphabetically by name.
6	The chosen inspector appears in the Property inspector floating palette. If the property inspector file defines the displayHelp() function, a small ? icon is displayed in the upper right corner of the inspector.
7	Dreamweaver calls the inspectSelection() function to gather information about the current selection and populate the inspector's fields.
8	Event handlers attached to the fields in the property inspector interface execute as the user encounters them. (For example, you may have an onBlur event that calls setAttribute() to set an attribute to the value just entered by the user.)